shipping details , and a fake invoice . But the file was actually a .zip archive that contained a JavaScript file which contained a Trojan dropper . The attackers continued to send outAttack.Phishingthe emails for about 12 hours . However , Gill gave Dropbox credit for responding quickly . `` I would say that after about an hour , we saw a lot of the links disabled , '' he said . `` After two hours , I was hard press to find a link that was n't disabled . '' Altogether , Gill estimated that the attackers had sent outAttack.Phishinghundreds of thousands , and possibly millions of messages . And since the messages arrivedAttack.Phishingright at the start of the workday in Europe , it would n't have taken long for potential victims to open the emails and click on the links . The attackers just need a small window of opportunity , he said . In addition to using spam filters , anti-virus , and training employees to identify malicious emails , there are other things enterprises can do to protect against this particular threat vector . For example , Gill said , companies could decide not to allow Dropbox in their environment . `` If you wanted to be aggressive , you could ban inbound Dropbox content links , '' he said . `` And if you decided that your organization was n't going to use it , you could easily make a change to your spam filter or your web filter to block access to Dropbox entirely . '' Dropbox does pose other potential security risks for enterprises as well , he added . `` Giving your employees freedom to use it is a risky thing , '' he said . `` Who knows what they 'll put in it , either on purpose or by accident .